1. Release History

August 13, 2008

LDAP version 6.1.3 rev. 080811 for Sitecore 5.3 is released.

Sitecore versions: tested with Sitecore 5.3.1 rev. 071114.

List of Changes:

Bugs fixed:

Fixed: When the Update Security button in LDAP module was pressed changes from extended fields of role weren’t transferred from Active Directory to Sitecore.

October 24, 2007

LDAP version 6.1.3 for Sitecore 5.3.1 is released.

Sitecore versions: tested with Sitecore 5.3.1 Build 070828.

List of Changes:

Bugs fixed:

Fixed: Nested groups is supported now

June 25, 2007

LDAP version 6.1.2 for Sitecore 5.3 is released.

List of Changes:

Bugs fixed:

Searching for groups with a quote in the name causes an error.
Login of a user that is a member of a group with a quote in the name causes an error.
Opening the “Configure Sitecore Client Security” section causes an error if Sitecore security database contains a user that is member of more than one group and one of them contains a quote in the name.

June 1, 2007

LDAP verion 6.1.1 for Sitecore 5.3 is released.

List of Changes:

Bugs fixed:

ldapmodule.dll doesn’t link to correct version of Sitecore.Kernel.
Upgrade package overwrites settings node.
Remove the Active Directory primary group from the group list in LDAP application.

August 25, 2006

LDAP version 6.1.0 for Sitecore 5.3 is released.

2. Known Issues

Warning entries appear in the Log file when you add a User or a group with LDAP application. For instance: 5532 18:24:44 WARN Could not resolve security item (AKLDAPgroup). Key: akldapgroup{A7DF04B4-4C4B-44B7-BE1E-AD901BD53DAD} 5532 18:24:44 WARN Could not resolve security item (alko). Key: alko{642C9A7E-EE31-4979-86F0-39F338C10AFB}
It’s not possible for an added User which has the “Password must be changed at next logon” option set in your directory to login to Sitecore (this only concerns the Live Validation and Mixed modes).
In the Mixed mode, the module allows an added User to login only if one of the groups, which he belongs to, is already added. Otherwise, an empty page with an error string appears.
User from the group which has a comma in the group name cannot login.
As a result of importing the AD-Group or AD-User whose name contains an '&' to Sitecore, no more groups and users can be found in the xml, but all the formerly imported groups and users remain in the DB.
When using single sign-on, the user must use Internet Explorer in order to automatically be recognized. For this to work, the user must either add the website to the "Local Intranet" zone or set the "User Authentication" setting in the browser to "Automatic logon with current user name and password".
User or group with a quote in the name cannot be added. To use groups and users with a quote in the name disable item name validation. Change ItemNameValidation setting: <setting name="ItemNameValidation" value="^[\w\*][\w\s\-\.\'\`]*$" />.

3. Limitations

It is required that your directory users contain a property informing which group the User is a member of – is default in AD and eDir; however, it can be a problem if you’re running in a Notes/Domino environment.
When a User tries to login to Sitecore, only valid direct memberships are registered, not the transitive (nested) ones.
The update for added fields works properly only if the LDAP field name, the value of the field’s Title property and the name of the field in the Security templates.xml file are identical.
Sitecore LDAP module does not support working across domains.